Setting up a hybrid infrastructure with vCloud Connector (vCC)

vCloud Connector combined with a vCloud API User provides you the ability to connect your On-Premise vSphere infrastructure with your public Cloud environment.

General Information

The following tasks are working with your On-Premise infrastructure and DCS:

Action from to Comment
Upload Template On-Premise DCS ---
Upload VM powered off On-Premise DCS Needs temp twice the storage of the VM being copied in OvDC
Download Template DCS On-Premise Becomes a VM in vCenter
Download VM powered off DCS On-Premise Needs temp twice the storage of the VM being copied in OvDC
Deploy from Template local On-Premise On-Premise ---
Deploy from Template DCS DCS DCS ---
Start/Stop/suspend VM local On-Premise On-Premise ---
Start/Stop/suspend VM remote On-Premise DCS ---
Open VM console from vCenter VCC local On-Premise On-Premise ---
Layer 2 Bridging On-Premise DCS Advanced VCC Server needed

VMware Documentation:


  • If you Upload or download a VM, check if the Hardware Version of this VM is compatible with the new environment:
  • The advanced features of vCloud Connector like content sync and stretch deploy need an additional license from VMware and are not tested with DCS.
  • For up- and download temp. twice the storage, of the VM being migrated, is needed. This is because a Template is created and copied in the background.
  • Templates cannot be deployed directly in DCS from remote, but you can choose the option to directly start deployment after upload
  • By default only Templates up to 40GB can be copied. For bigger templates both vCloud Connector Nodes have to be expanded first (
  • Content Sync and Layer 2 Bridging need Advanced vCloud Connector Server which is not tested with DCS.

Deployment steps

vCloud Connector consists of three distinct components: the vCloud Connector user interface, the vCloud Connector server, and vCloud Connector nodes.

Hybrid 1

Step 1:

Install the vCloud Connector Server in your on premise environment (

Step 2:

Install the vCloud Connector Node in your on premise environment.

Step 3:

Create a vCloud Director API user (see Section 2.9 vCloud Director API).

Step 4:

Install the vCloud Connector Node in your DCS environment (available in the public Catalog).

Step 5:

Ensure that all vCloud Connector Node have an internet connection.

Step 6:

Configure the vShield Edge in DCS to make the vCloud Connector Node available through internet. The vCloud Director Node in DCS must be available through internet with the following Ports enabled:

Source Destination Use Port
VCloud Connector Server vCloud Connector Node Communication 443
VCloud Connector Node vCloud Connector Node Communication, Upload 443, 8190
Admin Console (Client) vCloud Connector Appliances Admin Web Console 5480

Port 5480 is only required, if no Jumphost is available in DCS to manage the vCC Node through the Web Interface.

results matching ""

    No results matching ""